An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, My app Jewel Coloring Go! (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on July 31, 2026. However, today is Auguse 9, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

Hi, just want to make sure that my app is approved within the 48-hour period. It's nearing the tail end of it, and I would like to confirm that the app is good to go after a few iterations with App Review team and avoid further delays like before. Thanks!

Hi everyone, I’m looking for advice from developers who may have experienced a similar App Review situation. Our app, ASK VPN (Apple ID: 679*****), has been rejected multiple times, and I’m struggling to understand exactly what Apple is detecting. Initially, the app was rejected under Guideline 4.3(a) - Design - Spam. Apple first stated that the app shared a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. After we asked for clarification, Apple later stated that the app shared a similar binary, metadata, and/or concept with apps submitted by other developers, with only minor differences. To clarify an important point: we did not purchase this VPN source code from another developer, and we did not use a commercial VPN template, cloned project, or repackaged source code. ASK VPN was developed specifically for this project. I defined the product strategy, required functionality, user flow, and design direction myself, and used Codex AI as a development assistant to help implement the application. The codebase was created for ASK VPN rather than acquired from another developer or reused from an existing App Store application. Because of that, the earlier Guideline 4.3(a) rejection mentioning similarity to apps associated with other developers, including a terminated developer account, is particularly confusing to us. After the earlier rejection, we carefully reviewed and updated the application and added or improved product-specific functionality, including: Native iOS VPN implementation using Network Extension / Packet Tunnel ASK VPN account and profile integration Account status and expiry information First-use onboarding Terms and Conditions acceptance Privacy and VPN disclosure screens English and Myanmar localization In-app support and guided help Support diagnostic / Profile ID functionality Secure handling and redaction of sensitive VPN configuration data Updated app-specific UI and functionality We explained these changes to App Review and repeatedly asked which specific part was considered similar — source code, VPN implementation, framework, metadata, screenshots, assets, certificates, signing history, bundle identifier, backend behavior, or app functionality — but we did not receive a specific technical explanation. Now, on our latest submission, the rejection has changed to: Guideline 5.6 - Developer Code of Conduct Apple states: “The app contains features that appear to have been intentionally hidden during the review process.” This is especially confusing and concerning because we are not intentionally hiding any features from App Review. Another thing I have noticed is that the app enters “In Review” and then gets rejected very quickly, sometimes almost immediately. This has happened repeatedly. Because the rejection happens so quickly, I am wondering whether an automated or internal detection system may be flagging something related to the binary, code structure, Network Extension, account association, signing history, backend behavior, configuration, or another technical characteristic. At this point, we are willing to provide Apple with the complete source code of the application for technical review. We are also willing to provide: Complete iOS source code Network Extension / Packet Tunnel implementation Backend and API implementation Server-side configuration relevant to app behavior Feature flags and remote configuration Environment-specific configuration Authentication and account logic Source-control history Design and implementation records Complete feature documentation Test accounts and credentials Any other technical information Apple may require We would also be willing to provide access to a private source-code repository if Apple has an approved secure method for doing so. We are not looking for a way around App Review. We genuinely want to understand the exact issue, correct it properly, and fully comply with the App Store Review Guidelines. I would really appreciate advice from anyone who has experienced something similar. In particular: What can cause Apple to associate a newly developed app with apps from a terminated Developer Program account? Can common Network Extension / Packet Tunnel implementation patterns trigger similarity detection? Can AI-assisted code, standard iOS architecture, common libraries, or generated implementation patterns contribute to binary or source-code similarity? What can cause Apple to believe functionality is intentionally hidden during review? Could API responses, server-side behavior, feature flags, account states, device region, IP address, or review-environment differences cause this? Could signing history, certificates, bundle history, provisioning, or backend infrastructure create an association with another developer? Is there a way to request a deeper technical investigation or provide Apple with the complete source code? What is the best escalation path when repeated App Review replies do not identify the specific feature, code path, or behavior causing the rejection? Has anyone experienced a similar progression from Guideline 4.3(a) → Guideline 5.6? I’m honestly very discouraged after going through repeated rejections without being able to identify the root cause, but I want to resolve this correctly rather than keep making speculative changes and resubmitting. Any technical guidance or experience from developers who have dealt with a similar case would be greatly appreciated. Thank you.

It’s not only a normal review it’s an expedited review . We’re literally desperate to get this app approved yet it’s literally been a week to review the app . What do you do ? It says 90% of apps get reviewed in a day so how can we be waiting a week ? this is so horrible

I submitted my first public build (iOS 1.0) on July 30th for my game, Golfer's Pair-A-Dice (Apple ID: 6789222313) and it has been in "Waiting for Review" with no movement since then. I read that 24-48 hours is typical, but could take longer for first builds, but it seems like it hasn't even begun to be reviewed which is frustrating. Has anyone experienced similar wait times in the queue and had any success getting their app reviewed? I was hoping to launch on App Store and Google Play Store at same time and Google approved the app in 2 days so it has just been waiting for me to push, which I am waiting on Apple to approve so I can push both simultaneously.

Repeated Guideline 4.1(a) rejection for my game Hello, I’m looking for some advice regarding a repeated App Review rejection. My game is Pet Shop Owner Simulator. It was originally developed and published by me under Tri Creations on Google Play. I’m now submitting it to the App Store, but it has been rejected multiple times under Guideline 4.1(a) – Design – Copycats. The latest rejection states: “The app’s description, name, and icons includes references to Pet Shop Owner Simulator 3D.” The confusing part is that Pet Shop Owner Simulator 3D is the name of my own Android game. I have already explained this to App Review and provided documentation showing my ownership, but I continue to receive the same rejection. Could someone please advise how I can clarify this with App Review? In particular, I would like to understand whether Apple is referring to a specific third-party app or developer, or if there is something specific in my App Store metadata that I should change. Thank you.

After waiting on the phone for 3 hours, a rep answered and claimed headset issues and then just hung up and hasn’t bothered to call back. Not sure what sort of service I can expect here bust can anyone tell me why App Reviews take so long? They claim they are completed in 24-48 hours. It’s been nearly a week and nothing… Any help here will be greatly appreciated.

Hello App review Team, Our app has been submitted for up to a week now. Submission id - 8b32ad4d-9912-4f25-837c-13b15323a258. Kindly review. Thank you

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

After I set manual release, The app get approved and changed to Pending for Developer release status. I release the app but stuck in "Processing for distribution" now for 11 days. Please anything I can do to solve this, I edited the promotional text, changed price starting date and more. But nothing. I contact Apple support but still get an answer.

apple claimed that the game will be after review in 48 hours, i'm waiting for 2 weeks and i feel like i got scammed by apple. this is crazy! no response to emails and opening tickets. no one to talk to! its just an app update and its crazy! Date Submitted Aug 3, 2026 at 9:04 AM Submission ID b43c94ac-78a1-4e20-8da1-09f160b47313

Hello, I submitted my app for review on Aug 8, 2026 at 1:13 PM, and as of today (Aug 18, 2026), it is still sitting in "Waiting for Review" status — that's 10 days with no status change, no message in Resolution Center, and no email communication of any kind. Details: App: iOS App 1.0.0 (build 7) Submission ID: 8b91a820-3724-456e-a248-46ce84fb39ac Date Submitted: Aug 8, 2026, 1:13 PM Current Status: Waiting for Review (unchanged since submission) I understand review times are averages, not guarantees, and that App Review has been under heavier load recently (I've seen several other threads here reporting 9–17 day delays this month). Still, I wanted to check: Is there a known backlog affecting first-time / 1.0 submissions right now? Has anyone had success getting a status update by contacting Apple Developer Support directly, or does that not actually move the queue? Is there anything in the App Review Information (demo account, notes, compliance docs) that commonly causes silent delays like this rather than an outright rejection or reviewer note? Any insight from developers who've been through a similar wait — or from Apple — would be much appreciated. Happy to share more details if it helps others tracking similar delays this cycle. Thanks!

Hello everyone, I'm looking for some advice on how to handle an unusually long app review delay. I submitted my iOS app (Pressie Pro Express) for review on Aug 5, 2026, and it has been stuck ever since. I reached out to Apple Developer Support via the contact form on August 14th to ask for a status update, but I didn't receive a reply. I sent a follow-up message today (August 18th) and am still waiting to hear back. Has anyone else experienced significant review delays or unresponsiveness from support recently? Are there any alternative channels or best practices for escalating a review that seems to be completely stuck? Any insights or advice would be greatly appreciated! Thanks, Gisha

@Apple @AppleSupport I have been trying to enroll in the Apple Developer Program for over a month, but my enrollment is still not being processed. The payment has also NOT been deducted, and my enrollment/order remains incomplete. I have contacted Apple Support multiple times and followed everything the support team instructed me to do. Despite doing everything requested, I still cannot complete my enrollment. As a developer who has built an app and is ready to submit it to the App Store, this ongoing issue is extremely frustrating. I just want to enroll in the Apple Developer Program so I can publish my app. Apple, please review my case and help me complete my enrollment as soon as possible. Case ID: L544J6UGFS Enrollment ID: 20000135646296 I would really appreciate it if the Apple Developer team could look into this and provide a proper resolution. #Apple #AppleDeveloper #AppleSupport #AppStore #DeveloperProgram

Hello, I’m looking for guidance regarding an unusually long App Review process for my app, Auto Deal. The app was originally submitted on July 2, 2026. It eventually entered “In Review,” but remained there for an unusually long period without any update or decision. After waiting for a long time with no progress, I deleted the submission and uploaded it again. On the second submission, we again experienced a long delay. The app was eventually reviewed and rejected because of an issue that occurred when tapping the “Confirm” button inside the app. I immediately fixed the exact issue identified by App Review and submitted the corrected build. The corrected submission then entered “In Review,” but once again remained there for a long period without any further feedback or decision. After waiting again with no progress, I deleted the submission and uploaded a new build. When the same prolonged delay continued, I deleted that submission and submitted another fresh build. I understand that deleting and resubmitting can restart the review process. However, I only took these steps after repeatedly experiencing unusually long periods in review without any decision or explanation. Throughout this entire process, I have contacted Apple Developer Support multiple times and submitted three expedited review requests, but the issue remains unresolved. The app is complete and already available on Google Play. We have customers waiting for the iOS version, and this prolonged review process has significantly delayed our business launch. I am not requesting another expedited review through this post. I am trying to understand why this keeps happening and whether there is an issue with the app submission, my developer account, or the review process that requires action from my side. If an Apple engineer or App Review representative can look into this situation or advise me on the appropriate next step, I would greatly appreciate it. Thank you.

We are an established Apple Developer with multiple production apps. Over the past four weeks, every submission under our developer account—including both new apps and updates—has either remained in "Waiting for Review" or "In Review" significantly longer than expected. We have already: Contacted Apple Developer Support multiple times Been granted an expedited review Replied to all support cases Despite this, none of our submissions have progressed. I'm unsure if this could be related to an account-level review or another issue affecting our developer account. Has anyone else experienced similar issues? Thank You!

My first app submission has been in "Waiting for Review" for seven days with no status change and no communication from App Review. App: ForensicCrash Apple ID: 6796457936 Platform: iOS Version: 1.0 (build 8) Submitted: Aug 10, 2026 at 4:55 PM Submission ID: 305f86f9-8263-4e20-b908-825c26395103 The submission contains three items, all showing Waiting for Review: the app version, the subscription group (ForensicCrash Membership), and one auto-renewable subscription (Expert Annual). There is no rejection, no request for additional information, and nothing in the Resolution Center. Paid Apps and Free Apps agreements are Active, bank account is Active, and the W-9 is Active. Metadata, age rating, privacy labels, and export compliance are complete. Review notes include a working demo account, and the build has been running without issue. This is an initial release from a new organization account. Is there anything on my side holding this in the queue, or is this current backlog? Any guidance appreciated. Two notes on the mechanics. Open a Developer Support case first if you haven't — then add "Developer Support case number: 20000139746956" as the last line before the closing question, since posts carrying a case number tend to get picked up faster. And resist the urge to add anything about the delay being unacceptable or your launch timeline being at risk; the posts that draw the "we're investigating and will contact you in App Store Connect" reply read exactly like the above — flat, complete, easy to act on.

Hello, Our app has been in "Waiting for Review" for a long time with no movement and no open items in the Resolution Center. For reference, two other apps submitted from the same developer account during this period were reviewed and approved within 2 days, the timeframe we normally experience. Only this submission remains stuck. Could someone from App Review please check the status of this submission and confirm it is not blocked in the queue? We are happy to provide any additional information. Thank you.

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

Hello, I am seeing sever delay in app review completion of my app. The version I submitted for review is pending since Aug 14th, but later that I had one version pending like 5 days without answer. This is the first time it happened like this as earlier it was quicker. I tried to contact apple through support email but have not received any update. Any suggestions on what I can do? App name is: Comeloia IA cuenta calorías and ID: 6755640668 Thank you.